Image processing system, method of controlling image processing system, and storage medium

ABSTRACT

An image processing system includes a server to control a plurality of processes performable in the image processing system, a first image forming apparatus communicable with the server, and a second image forming apparatus communicable with the server. The server includes a first memory to store first image processing data, and a first processor to generate first image drawing information based on the first image processing data. The second image forming apparatus includes a second memory to store second image processing data, a second processor to generate second image drawing information based on the second image processing data, and a print engine to perform the image forming operation of the second image forming apparatus based on the second image drawing information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/334,530, filed on Oct. 26, 2016, which claims priority pursuant to 35U.S.C. § 119(a) to Japanese Patent Application No. 2015-219358, filed onNov. 9, 2015 in the Japan Patent Office, the entire contents of whichare incorporated herein by reference in entirety.

BACKGROUND

Technical Field

This disclosure relates to an image processing system, a control methodof the image processing system, a method of processing image, and astorage medium of a program of f controlling the image processingsystem.

Background Art

Systems that can define and control various processes for generating aprinted product by using a data format such as job definition format(JDF) are known. This system can collectively control various types ofprinters such as offset printers and digital printers. This system isreferred to as a hybrid work flow (HWF) system, and a server thatcontrols the HWF system is referred to as a HWF server.

In this HWF system, the offset printer including a raster imageprocessor (RIP) engine and the digital printer including a raster imageprocessor (RIP) engine are operated based on the same print data, inwhich the output result of the offset printer and the output result ofthe digital printer are required to be same in various properties suchas font, color tone, and layout.

However, the RIP engine of the offset printer that generates rasterdata, which is to be used for the printing operation, based on the printdata, and the RIP engine of the digital printer that generates rasterdata, which is to be used for the printing operation, based on the printdata, are different RIP engines, and thereby the output result of thedigital printer may become different.

The HWF system can be disposed with a plurality of RIP engines havingdifferent processing capabilities, in which the suitable IP engines canbe selected. For example, JP-2012-108821-A discloses a technology thatraster data generated by the RIP processing of the plurality of RIPengines are compared, and the to-be-used RIP engine is determined basedon a comparison result.

Further, JP-2004-246583-A discloses a technology that embeds graphicdata of font into print data so that the output results of differentapparatuses, installed with different font data, can become the sameresult.

When the offset printer outputs an image, a RIP engine disposed in theHWF server generates the raster data (hereinafter, RIP processing), andtransmits the raster data to a computer-to-plate (CTP) of the offsetprinter that generates a plate to be used at the offset printer. Whenthe digital printer outputs an image, a digital front end (DFE) of thedigital printer receives print data and performs the RIP processing, andthen a printer engine performs the printing operation.

Therefore, it is required that the process result of the RIP engine thatgenerates the data to be transferred to the CTP and the process resultof the RIP engine of the DFE become the same as much as possible. Thetechnology of JP-2012-108821-A requires a comparing process of theraster data, which increases the processing time. The technology ofJP-2004-246583-A is related only to the font, and not related theoverall properties of the printing operation.

SUMMARY

As one aspect of the present invention, the image processing system isdevised. The image processing system includes a server to control aplurality of processes performable in the image processing system, afirst image forming apparatus communicable with the server, and a secondimage forming apparatus communicable with the server. The serverincludes a first memory to store first image processing data beingapplicable to an image process to be performed on a target image to beoutput, and a first processor to generate first image drawinginformation based on the first image processing data, to be referred bythe first image forming apparatus in performing an image formingoperation based on output target image information. The second imageforming apparatus includes a second memory to store second imageprocessing data being applicable to the image process to be performed onthe target image to be output, a second processor to generate secondimage drawing information based on the second image processing data, tobe referred by the second image forming apparatus in performing an imageforming operation based on the output target image information receivedfrom the server, and a print engine to perform the image formingoperation of the second image forming apparatus based on the secondimage drawing information.

As another aspect of the present invention, a method of controlling animage processing system including a server to control a plurality ofprocesses performable in the image processing system, a first imageforming apparatus communicable with the server, and a second imageforming apparatus communicable with the server, is devised. The methodincludes generating first image drawing information in the server basedon first image processing data stored in a first memory of the server,the first image processing data being applicable to an image process tobe performed on a target image to be output, transmitting output targetimage information from the server to the second image forming apparatus,transmitting the output target image information and the first imagedrawing information from the server to the first image formingapparatus, generating second image drawing information in the secondimage forming apparatus based on the output target image informationreceived from the server and second image processing data stored in asecond memory of the second image forming apparatus, the second imageprocessing data being applicable to the image process to be performed tothe target image to be output, performing the image forming operation byusing the second image forming apparatus based on the second imagedrawing information.

As another aspect of the present invention, a non-transitory storagemedium storing a program that, when executed by a computer, causes thecomputer to execute a method of controlling an image processing systemincluding a server to control a plurality of processes performable inthe image processing system, a first image forming apparatuscommunicable with the server, and a second image forming apparatuscommunicable with the server, is devised. The method includes generatingfirst image drawing information in the server based on first imageprocessing data stored in a first memory of the server, the first imageprocessing data being applicable to an image process to be performed ona target image to be output, transmitting output target imageinformation from the server to the second image forming apparatus,transmitting the output target image information and the first imagedrawing information from the server to the first image formingapparatus, generating second image drawing information in the secondimage forming apparatus based on the output target image informationreceived from the server and second image processing data stored in asecond memory of the second image forming apparatus, the second imageprocessing data being applicable to the image process to be performed tothe target image to be output, performing the image forming operation byusing the second image forming apparatus based on the second imagedrawing information.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete appreciation of the disclosure and many of the attendantadvantages and features thereof can be readily obtained and understoodfrom the following detailed description with reference to theaccompanying drawings, wherein:

FIG. 1 is a schematic diagram illustrating a configuration of a systemof an example embodiment of the present invention;

FIG. 2 is a schematic diagram illustrating a hardware configuration ofan information processing apparatus of an example embodiment of thepresent invention;

FIG. 3 is an example of JDF information of an example embodiment of thepresent invention;

FIG. 4 is a schematic diagram illustrating a functional configuration ofa HWF server of an example embodiment of the present invention;

FIG. 5 is an example of workflow information of an example embodiment ofthe present invention;

FIG. 6 is a schematic diagram illustrating a functional configuration ofa DFE of an example embodiment of the present invention;

FIG. 7 is an example of a conversion table of an example embodiment ofthe present invention;

FIG. 8 is an example of RIP parameter of an example embodiment of thepresent invention;

FIG. 9 is a schematic diagram illustrating a functional configuration ofa RIP engine of an example embodiment of the present invention;

FIG. 10 is another functional configuration of a RIP engine of anexample embodiment of the present invention;

FIG. 11 is a sequential chart for an operation flow of a HWF system ofan example embodiment of the present invention;

FIG. 12 illustrates an example of a dividing pattern of image data;

FIG. 13 is a flow chart showing the steps of processing in the DFE of anexample embodiment of the present invention;

FIG. 14 is flow chart showing the steps of the RIP processing of anexample embodiment of the present invention;

FIG. 15 is a flow chart illustrating the steps of a process oftransmitting RIP resource data stored in the HWF server to the DFE.

FIG. 16 is an example of job data adding referring instruction of RIPresource data

FIG. 17 is an example of job data adding RIP resource data;

FIG. 18 is an example of modification of software when a RIP engine isdeveloped in the software development process;

FIG. 19 is an example of a table associating capabilities installed forRIP engines, and the differences of output result of RIP processing

FIG. 20 is a flow chart illustrating the steps of a process ofdetermining a device or apparatus to perform the RIP processing by usingthe HWF server; and

FIG. 21 is a flow chart illustrating the steps of a process of s ofdetermining the device or apparatus to perform the RIP processing byusing the DFE.

The accompanying drawings are intended to depict exemplary embodimentsof the present invention and should not be interpreted to limit thescope thereof. The accompanying drawings are not to be considered asdrawn to scale unless explicitly noted, and identical or similarreference numerals designate identical or similar components throughoutthe several views.

DETAILED DESCRIPTION

A description is now given of exemplary embodiments of the presentinvention. It should be noted that although such terms as first, second,etc. may be used herein to describe various elements, components,regions, layers and/or sections, it should be understood that suchelements, components, regions, layers and/or sections are not limitedthereby because such terms are relative, that is, used only todistinguish one element, component, region, layer or section fromanother region, layer or section. Thus, for example, a first element,component, region, layer or section discussed below could be termed asecond element, component, region, layer or section without departingfrom the teachings of the present invention.

In addition, it should be noted that the terminology used herein is forthe purpose of describing particular embodiments only and is notintended to be limiting of the present invention. Thus, for example, asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Moreover, the terms “includes” and/or “including”, when usedin this specification, specify the presence of stated features,integers, steps, operations, elements, and/or components, but do notpreclude the presence or addition of one or more other features,integers, steps, operations, elements, components, and/or groupsthereof.

Furthermore, although in describing views illustrated in the drawings,specific terminology is employed for the sake of clarity, the presentdisclosure is not limited to the specific terminology so selected and itis to be understood that each specific element includes all technicalequivalents that operate in a similar manner and achieve a similarresult. Referring now to the drawings, one or more apparatuses orsystems according to one or more example embodiments are describedhereinafter.

A description is given of an image processing system of one or moreexample embodiments of the present invention with reference to drawings.The image processing system includes, for example, an offset printer,and a digital printer, and a server, in which both of the offset printerand the digital printer can be controlled by the same server.Hereinafter, this image processing system is referred to a hybrid workflow (HWF) system. In the HWF system, a raster image processor (RIP)engine disposed in a digital front end (DFE) that controls the digitalprinter, and a raster image processor (RIP) engine disposed in the HWFserver can employ the same type of RIP engine, and the digital printerexecutes a printing operation in this HWF system under the conditionthat the same type of RIP engine is disposed at the differentapparatuses configuring the HWF system. In this description, the sametype of RIP engine may mean two or more RIP engines have substantiallysame processing capabilities, and thereby the two or more RIP enginesare not required to have the exact same processing capabilities.

(First Example Embodiment)

FIG. 1 is a schematic configuration of the HWF system of one or moreexample embodiments of the present invention. As illustrated in FIG. 1,the HWF system includes, for example, a digital printer 1, an offsetprinter 2, a post-processing apparatus 3, HWF servers 4 a and 4 b(hereinafter, collectively referred to HWF server 4 as required), andclient terminals 5 a and 5 b (hereinafter, collectively referred toclient terminal 5 as required) connectable with one to another via anetwork.

The digital printer 1 is an example of printers that can generate andoutput images using an electrophotography method or an inkjet methodwithout using a plate. The digital printer 1 includes, for example, adigital front end (DFE) 100, and a digital engine 150. The DFE 100 canbe used as a controller for controlling an image generation and output,which means the DFE 100 can be used as an image generation-outputcontrol apparatus, in which the DFE 100 controls the digital engine 150to perform a print output operation or printing operation. Further, thedigital engine 150 can be used as a device for generating an image,which may be referred to as an image generator or print engine.Therefore, the DFE 100 includes a raster image processor (RIP) enginethat generates raster data that is referred or used by the digitalengine 150 when performing the print output operation. The raster datais used as drawing information or image drawing information.

The offset printer 2 is an example of printers that can generate andoutput images by using a plate. The offset printer 2 includes, forexample, a computer-to-plate (CTP) 200, and an offset engine 250. TheCTP 200 generates a plate based on the raster data. The offset engine250 can perform an offset printing by using the plate generated by theCTP 200.

The post-processing apparatus 3 can perform various post-processing suchas punch, staple, and bookbinding to printed sheets output from thedigital printer 1 and/or the offset printer 2. Further, thepost-processing apparatus 3 can perform a sheet folding and sheetcutting when the offset printer 2 outputs sheets processed with theimposition.

The HWF server 4 is a server installed with an HWF software program thatis used to manage an image processing operation such as inputting of jobdata including target image data of a print output operation, processingof the print output operation, and post-processing. The HWF server 4manages the above mentioned various processing using informationgenerated by using a job definition format (JDF), which is referred toas “JDF information.” The HWF server 4 can be used as a processexecution control apparatus or a processing control apparatus.

The HWF server 4 further includes a raster image processor (RIP) enginein the HWF server 4. When the offset printer 2 performs an offsetprinting operation (i.e., print output operation), the RIP engine 420 inthe HWF server 4 generates raster data, and transmits the generatedraster data to the CTP 200, in which the RIP engine 420 generates theraster data as first image drawing information.

Further, when the digital printer 1 performs a printing operation (i.e.,print output operation), the HWF server 4 transmits data to the DFE 100.Since the DFE 100 has the RIP engine 120 as described above, the digitalprinter 1 can perform the print output operation even when the HWFserver 4 transmits print data that is not processed by the RIPprocessing in the HWF server 4 to the DFE 100.

As to the HWF system, the same print data may be used for the printoutput operation by the digital printer 1 and the print output operationby the offset printer 2. For example, one book can be printed by theprint output operation of the digital printer 1 and the print outputoperation by the offset printer 2, in which the print output operationby the digital printer 1 and the print output operation by the offsetprinter 2 are performed independently. In this configuration, if theprint output operation result by the digital printer 1 and the printoutput operation result by the offset printer 2 become different such asdifferent fonts and color values, a user feels oddness on a printedproduct. Therefore, it is preferable that the print output operationresult by the digital printer 1 and the print output operation result bythe offset printer 2 become substantially the same one.

The differences of print output operation results by using differentdevices or apparatuses may occur due to the RIP processing. Therefore,by using the same RIP engine for data or information processing at thedigital printer 1 and data or information processing at the offsetprinter 2, the differences between the print output operation result bythe digital printer 1 and the print output operation result by theoffset printer 2 can be reduced or minimized.

Specifically, the RIP engine disposed in the HWF server 4 is an enginethat can process data or information for both of the digital printer 1and the offset printer 2, and the RIP engine disposed in the HWF server4 can perform common processes for the digital printer 1 and the offsetprinter 2. Further, the RIP engine disposed in the DFE 100 and the RIPengine disposed in the HWF server 4 employ the same type of RIP engine.

With employing this configuration, the HWF server 4 and the DFE 100 aredisposed with the same RIP engine having the same processing capability.Therefore, when the print output operation by the digital printer 1 isto be performed, the RIP processing by the HWF server 4 and the RIPprocessing by the DFE 100 can be selectively combined and performed.

An operator of the HWF system can operate the HWF server 4 by using theclient terminal 5, in which the client terminal 5 can be used as aninformation processing terminal. The client terminal 5 can be anyterminal devices or apparatuses such as a general personal computer(PC), but not limited hereto. The operator operates the client terminal5 to display a graphic user interface (GUI) used for operating the HWFserver 4, in which the GUI can be used to input data and setting the JDFinformation. The JDF information sets information for processing in theHWF system, and the JDF information may be referred to as processsetting information.

A description is given of a hardware configuration of the DFE 100, theHWF server 4, and the client terminal 5 known as information processingapparatuses with reference to FIG. 2. As illustrated in FIG. 2, theinformation processing apparatus has a configuration similar to generalservers and personal computers (PC). Specifically, the informationprocessing apparatus includes, for example, a central processing unit(CPU) 10, a random access memory (RAM) 20, a read only memory (ROM) 30,a hard disk drive (HDD) 40, and an interface (I/F) 50 that areconnectable or couplable by a bus 80. Further, a liquid crystal display(LCD) 60 and an operation unit 70 are connectable or couplable to theinterface I/F 50.

The CPU 10 is a computing unit such as circuitry or a processor thatcontrols the entire operations of the information processing apparatus.The RAM 20 is a volatile memory, to which information can be read andwritten with high speed, and the CPU 10 uses the RAM 20 as a workingarea when processing information or data. The ROM 30 is a non-volatilememory used as a read only memory, in which various programs such asfirmware are stored. The HDD 40 is a non-volatile memory, to whichinformation can be read and written. For example, the HDD 40 stores anoperating system (OS), various control programs, and applicationprograms.

The I/F 50 is connected or coupled to the bus 80, various units andnetworks, and controls the connection or coupling. The LCD 60 is a userinterface that a user can check the status of the information processingapparatus visually. The operation unit 70 is a user interface such as akey board and a mouse that a user can input information to theinformation processing apparatus. Since the HWF server 4 is used as aserver, a user interface such as LCD 60 and operation unit 70 can beomitted for the HWF server 4.

As to the above described hardware configuration of the informationprocessing apparatus, the CPU 10 performs computing by loading programsstored in the ROM 30, the HDD 40, and/or an external memory such as anoptical disk on the RAM 20 to configure a software control unit. With acombination of the software control unit and the hardware, functionalblocks required for the DFE 100, the HWF server 4, and the clientterminal 5 can be devised.

A description is given of the JDF information with reference to FIG. 3.FIG. 3 is an example of the JDF information. As illustrated in FIG. 3,the JDF information includes, for example, “job information” related toa job execution, “edit information” related to the raster data, and“finishing information” related to the post-processing. Further, the JDFinformation includes, for example, information of “RIP status,” “RIPdevice designation,” and “device designation.”

As illustrated in FIG. 3, the “job information” includes information of,for example, “number of copies,” “number of total pages,” and “RIPcontrol mode.” The “number of copies” is information that designates thenumber of copies of an output target data to be output as a printedproduct. The “number of total pages” is information that designates thenumber of total pages included in one printed product. The “RIP controlmode” indicates a control mode of the RIP processing, in which a “pagemode” and a “sheet mode” can be designated for the “RIP control mode.”

The “edit information” includes, for example, “orientation information,”“print face information,” “rotation,” “enlarge/reduce,” “imageposition,” “layout information,” “margin information,” and “crop markinformation.” The “orientation information” is information thatdesignates a printing orientation of a sheet such as “portrait(vertical)” and “landscape (horizontal).” The “print face information”is information that designates a to-be-printed face such as “duplex” and“one face.”

The “rotation” is information that designates a rotation angle of animage of an output target data. The “enlarge/reduce” is information thatdesignates a size change ratio of an image of an output target data. Asto the “image position,” “offset” is information that designates anoffset of an image of an output target data, and “position adjustmentinformation” is information that designates a position adjustment valueof an image of an output target data.

The “layout information” includes, for example, “custom impositionarrangement,” “number of pages,” “page sequence information,” and “creepposition information.” The “custom imposition arrangement” isinformation that designates an arrangement on a custom face. The “numberof pages” is information that designates the number of pages printed inone sheet. For example, when images of two pages are condensed andprinted on one face of a single sheet, information of “2 in 1” isdesignated. The “page sequence information” is information thatdesignates a sequence of pages to be printed. The “creep positioninformation” is information that designates a value related to anadjustment of a creep position.

The “margin information” is information that designates a value relatedto a margin such as a fit box and a gutter. The “crop mark information”includes, for example, “center crop mark information” and “corner cropmark information.” The “center crop mark information” is informationthat designates a value related to a center crop mark. The “corner cropmark information” is information that designates a value related to acorner crop mark.

The “finishing information” includes, for example, “Collateinformation,” “staple/binding information,” “punch information,”“folding information,” “trimming,” “output tray information,” “inputtray information,” and “cover sheet information.” The “Collateinformation” is information that designates a page-by-page printing or adocument-by-document printing when one document is to be printed with aplurality of numbers of copies.

The “staple/binding information” is information that designates aprocess related to staple/binding. The “punch information” isinformation that designates a process related to punch. The “foldinginformation” is information that designates a process related to foldingof sheets. The “trimming” is information that designates a processrelated to trimming of sheets.

The “output tray information” is information that designates an outputtray. The “input tray information” is information that designates aninput tray. The “cover sheet information” is information that designatesa process related to a cover sheet.

The “RIP status” is used as execution status information indicatingwhether each of internal processes included in the RIP processing isalready executed. In an example case of FIG. 3, the internal processesof RIP processing includes items such as “pre-fright,” “normalize,”“font,” “layout,” “mark,” “CMM,” “Trapping,” “Calibration,” and“Screening,” and a processing status is set for each of the internalprocesses of RIP. In the example case of FIG. 3, the processing statusof “NotYet” is set for the “RIP status” to indicate that “a concernedprocess is not yet processed”. When each of the internal processes ofRIP is executed, the status is updated to “Done” to indicate that “theconcerned process is already processed.”

The “RIP device designation” is information that designates a device toperform each of the internal processes of RIP processing. In the examplecase of FIG. 3, the “RIP device designation” designates the HWF server 4or the DFE 100 to perform each of the internal processes of RIPprocessing. As illustrated in FIG. 3, each one of the internal processesof RIP processing is performed by setting any one of the “HWF server”and “DFE” for each of the internal processes of RIP processing. Further,when the “DFE” is set as the RIP device, information designating any oneof a plurality of RIP engines installed in the DFE 100 can be designatedsuch as “DFE (engine A)” and DFE (engine B).

The “device designation” is information that designates a device thatexecutes a print job. In the example case of FIG. 3, the “digitalprinter” is designated to execute the print job. Further, the JDFinformation can include various information other than informationillustrated in FIG. 3, which will described later in this description.

The JDF information illustrated in FIG. 3 can be generated by anoperator. For example, the operator operates the client terminal 5 todisplay a GUI of the HWF server 4, and then the operator sets variousitems of the JDF information by using the GUI. The RIP engine disposedin the HWF server 4 and the RIP engine disposed in the DFE 100 canperform the RIP processing based on the JDF information. Further, thepost-processing apparatus 3 can perform the post-processing based on theJDF information. Further, when a job is input to the HWF server 4 froman external system and software, the job assigned with JDF informationmay be input.

A description is given of a functional configuration of the HWF server 4with reference to FIG. 4. As illustrated in FIG. 4, the HWF server 4includes, for example, a HWF controller 400, and a network interface(I/F) 401. The network I/F 401 is an interface used for communicatinginformation between the HWF server 4 and other devices or apparatusesavailable for use via a network.

The HWF controller 400 manages various processing such as an acquisitionof job data of a print target, a generation of a print job, a managementof a workflow, and an allocation of job data to the digital printer 1and the offset printer 2. A process that job data of a print target isinput to the HWF server 4 and acquired by the HWF controller 400 is aprocess of inputting data to the HWF system. The HWF controller 400 canbe implemented by installing a specific software program such as a HWFsoftware program in the information processing apparatus.

As illustrated in FIG. 4, the HWF controller 400 includes, for example,a system controller 410, a data receiver 411, a user interface (UI)controller 412, a job controller 413, a job data storage 414, a deviceinformation communication unit 415, a device information manager 416, adevice information storage 417, a workflow controller 418, a workflowinformation storage 419, a RIP engine 420, a job communication unit 421,and a RIP resource storage 422. The system controller 410 controls theHWF controller 400 entirely. Therefore, the system controller 410transmits commands to each of the units in the HWF controller 400 toimplement each of the above described functions or capabilities of theHWF controller 400. The data receiver 411 receives to-be-printed jobdata from other system, or to-be-printed job data input by an operationof an operator.

The UI controller 412 controls an operation operable by an operator viathe client terminal 5. For example, a graphical user interface (GUI)used for operating the HWF server 4 is displayed on the client terminal5, and the UI controller 412 acquires information of an operation workto the GUI displayed on the client terminal 5 via a network.

The UI controller 412 reports information of the operation acquired viathe network to the system controller 410. The display of GUI on theclient terminal 5 can be implemented by executing a software programinstalled in the client terminal 5, or by supplying information to theclient terminal 5 from the UI controller 412 via the network.

The operator operates the GUI displayed on the client terminal 5 toselect job data to be input as a print target. Then, the client terminal5 transmits the selected job data to the HWF server 4, and then the datareceiver 411 acquires the selected job data. The system controller 410registers the job data acquired by the data receiver 411 to the job datastorage 414.

When the job data is to be transmitted from the client terminal 5 to theHWF server 4, the job data is generated in the client terminal 5 basedon document data and/or image data selected at the client terminal 5,and then the job data is transmitted to the HWF server 4. The job datais described, for example, by page description language (PDL) formatsuch as portable document format (PDF) and PostScript.

Further, the client terminal 5 can transmit data of a print target tothe HWF server 4 by using an application specific data format or ageneral image data format. In this configuration, the system controller410 instructs the job controller 413 to generate job data based on theacquired data. The job controller 413 generates the job data based onthe data of print target by using the RIP engine 420.

As described above, the data of print target registered in the job datastorage 414 is PDL information. The PDL information can be, for example,primary data generated from the data of print target, or intermediatedata, which is processed to the middle of the RIP processing. Theseinformation can be used as information of an output target image (i.e.,output target image information). For example, the intermediate data canbe stored in the job data storage 414 when the job data is processed tothe middle of the RIP processing that is already started in the HWFserver 4, or when the job data is registered in the HWF server 4 with acondition of the intermediate data. Hereinafter, the “PDL information”indicates primary data that is not yet processed by the RIP processing,and the intermediate data indicates data that is processed to the middleof the RIP processing (i.e., processing-not-completed data) in thisdescription.

Further, as described above, the JDF information illustrated in FIG. 3can be set and generated by an operation of an operator to the GUIdisplayed on the client terminal 5. Further, when a job is input to theHWF server 4 from an external system and software, the JDF informationmay be assigned to the job. The generated or acquired JDF informationcan be received by the data receiver 411 with the PDL information as thejob data. The system controller 410 correlates the acquired JDFinformation and PDL information, and registers the JDF information andPDL information to the job data storage 414.

In this description, attribution information indicating job contents isdescribed by using the JDF information, but not limited hereto. Forexample, the attribution information indicating job contents can bedescribed by using other format such as print production format (PPF).

Further, the system controller 410 can divide the received job data asrequired based on an operation of an operator to a GUI displayed on theclient terminal 5. For example, the system controller 410 can divide thereceived job data into a discrete unit of printing portion such as aunit of “page,” and each one of the divided job data can be registeredin the job data storage 414 as sub-job data, in which the job data isconfigured by the plurality of the sub-job data.

When an output-destination device is selected for each of the sub-jobdata by an operation of an operator to a GUI displayed on the clientterminal 5, the operator's selection result is correlated with thesub-job data, and then stored in the job data storage 414. Theoutput-destination device can be set selectively for each of the sub-jobdata. For example, the digital printer 1 can be selected for printingsub-job data corresponding to a cover of the received job data, and theoffset printer 2 can be selected for printing sub-job data correspondingto a main contents of the received job data.

The device information manager 416 acquires information of availabledevices or apparatuses included in the HWF system such as the digitalprinter 1, the offset printer 2, the post-processing apparatus 3 or thelike, and the device information manager 416 stores information of theavailable devices or apparatuses in the device information storage 417,and manages the information of the available device or apparatuses. Theinformation of available devices includes, for example, a networkaddress allocated to each device when the device is connected or coupledto the network, and device capability information of each device. Thedevice capability information includes, for example, printing speed,available post-processing capability, and operational condition.

The device information communication unit 415 can acquire information ofthe available devices included in the HWF system at regular intervalsvia the network I/F 401. With this configuration, the device informationmanager 416 can update information of the available devices stored inthe device information storage 417 at regular intervals. Therefore, evenif the information of the available devices changes over time, theinformation stored in the device information storage 417 can be updatedand maintained at the latest status.

The workflow controller 418 determines an execution sequence of aplurality of processes to be executed for the job data registered in thejob data storage 414 in the HWF system, and stores information of theexecution sequence in the workflow information storage 419. Based on theexecution sequence set for each of processes in a workflow in advance,the workflow controller 418 can control the execution sequence, in whichwhen one process completes, the sequence proceeds to the next process.

The workflow information stored in the workflow information storage 419specifies the execution sequence of each of processes executable in theHWF system, in which the processes are sequentially arranged based onthe designated execution sequence. FIG. 5 is an example of workflowinformation. Further, parameters, which are used when each of theprocesses is executed, can be designated as the JDF information as abovedescribed. The workflow information storage 419 registers the workflowinformation in advance based on an operation of an operator to the GUIdisplayed on the client terminal 5.

An execution instruction of the job data, registered in the HWF server4, is reported to the system controller 410 via the UI controller 412based on an operation of an operator to the GUI displayed on the clientterminal 5. With this configuration, the system controller 410 canselect the above described output-destination device.

When the output-destination device is selected by using the GUIdisplayed on the client terminal 5 as described above, the systemcontroller 410 selects the output-destination device based on adesignation of the output-destination device. Further, theoutput-destination device can be selected automatically based on acomparison of job contents and a device property.

When the output-destination device is selected automatically based onthe comparison of job contents and the device property, the systemcontroller 410 acquires information of device available for use from thedevice information manager 416. When the output-destination device isdetermined as above described, the system controller 410 assignsinformation indicating the determined output-destination device to theJDF information.

After determining the output-destination device, the system controller410 instructs the workflow controller 418 to execute a job. In thisprocess, the workflow information, registered in the workflowinformation storage 419 in advance based on then operation of theoperator, can be used. Further, a new workflow information can begenerated and then used based on contents set by the operator.

After receiving the execution instruction from the system controller410, the workflow controller 418 instructs the job controller 413 toexecute each of the processes based on the designated execution sequenceof the designated workflow information or the newly generated workflowinformation. Therefore, the workflow controller 418 and the jobcontroller 413 can be collectively used as a process executioncontroller.

After receiving the execution instruction, the job controller 413 inputsthe above described PDL information and JDF information to the RIPengine 420 to execute the RIP processing. The JDF information includesinformation that indicates which one of the HWF server 4 and the DFE 100is used for processing each of internal processes of the RIP processingusing the RIP engine.

The job controller 413 refers or checks allocation information of theRIP processing included in the JDF information. If one processdesignated by the workflow controller 418 is a process to be executed bythe HWF server 4, the job controller 413 instructs the RIP engine 420 toexecute the designated one process. Based on the instruction from thejob controller 413, the RIP engine 420 executes the RIP processing basedon parameters designated in the JDF information.

After executing the RIP processing, the RIP engine 420 updates the RIPstatus of each of the processes executed by the RIP processing. Withthis configuration, the status of each of the internal processes of theRIP processing executed by the HWF server 4 is changed from “NotYet” to“Done.” The RIP engine 420 can be used as a control-side image drawinginformation generator or control-side drawing information generator.

The RIP-executed result data generated by executing the RIP processingis any one of PDL information, intermediate data, and raster data. Anyone of the PDL information, intermediate data, or raster data can begenerated depending on the internal process of the RIP processing.Specifically, as the sequence proceeds, the intermediate data isgenerated from primary data such as PDL information, and the raster datais generated as final data from the intermediate data. The RIP-executedresult data is correlated with a being-executed job, and stored in thejob data storage 414.

When each one of the internal processes of RIP processing is completed,the RIP engine 420 reports the completion of each one of the internalprocesses to the job controller 413, and the job controller 413 reportsthe completion of each one of the internal processes to the workflowcontroller 418. With this configuration, the workflow controller 418starts to control a subsequent or next process based on the workflowinformation.

If the job contents received from the workflow controller 418 is arequest to the other system, the job controller 413 inputs job data,compatible to the other system, to the job communication unit 421, andinstructs the job communication unit 421 to transmit the job data. Ifthe job data is to be transmitted to the offset printer 2, the job dataof a print target is converted to the raster data, and then the rasterdata is transmitted to the offset printer 2 as the job data.

Further, if the job data is to be transmitted to the digital printer 1,the job controller 413 inputs the job data to the job communication unit421 while designating a RIP engine having capabilities compatible withthe RIP engine 420 from a plurality of the RIP engines included in theDFE 100. With this configuration, the job communication unit 421transmits the job data to the DFE 100 by designating the RIP engine thatis the same type of the RIP engine 420.

The job communication unit 421 transmits the job data such as a packageof PDL information and JDF information or a package of intermediate dataand JDF information to the DFE 100. Further, the PDL information orintermediate data can be transmitted to the DFE 100 separately from theJDF information, in which the PDL information or intermediate data canbe prepared as external resource data, and the JDF information caninclude universal resource locators (URL) indicating a storage area ofthe PDL information or a storage area of intermediate data. In thisconfiguration, the DFE 100 that receives the JDF information can accessthe storage area specified by the URL to acquire the PDL information orintermediate data.

A description is given of a functional configuration of the DFE 100 withreference to FIG. 6. When the DFE 100 receives job data from the HWFserver 4, the DFE 100 controls the received job, an execution of the RIPprocessing, and the digital engine 150. The HWF server 4 transmits thejob data to the DFE 100 and instructs the DFE 100 to execute a printoutput operation by using the digital engine 150. Therefore, the DFE 100can be used as a device to provide digital printing capability to theHWF server 4.

The job control performable by the DFE 100 is a process of controlling aseries of processes such as a reception of job data, an analysis of JDFinformation, a generation of raster data, and a print output operationby the digital engine 150. The execution control of the RIP processingis a process of controlling the RIP engine to execute the RIP processingbased on information generated by the analysis of the JDF informationand PDL information.

The information generatable by analyzing the JDF information means thatinformation used for the RIP processing is extracted from the JDFinformation (FIG. 3), and is then converted to a data format processableby the DFE 100, which is referred to “job attribute in DFE” in thisdescription. By executing the RIP processing by using the job attributein DFE and the PDL information, the intermediate data and raster datacan be generated.

The control of the digital engine 150 is a process of transmittingraster data and at least a part of the above described job attribute inDFE to the digital engine 150, and executing the print output operationby the digital engine 150. These capabilities can be implemented by eachof units illustrated in FIG. 6. Each of the units illustrated in FIG. 6can be implemented by activating the hardware (FIG. 2) by loadingprograms stored in the ROM 30 on the RAM 20 and executing the loadedprograms by using the CPU 10.

As illustrated in FIG. 6, the DFE 100 includes, for example, a networkI/F 101, a DFE controller 110, and a display 102. The DFE controller 110includes, for example, a job receiver 111 including a plurality ofspecific job receiving units 112, a system controller 113, a job datastorage 114, a UI controller 115, a job controller 116, a JDF analyzer117, a RIP unit 118, a RIP controller 119, a RIP engine 120, an imagestorage 121, a printer controller 122, a device information manager 123,and a device information communication unit 124, and a RIP resourcestorage 125.

The DFE 100 can include a plurality of RIP engines therein, and each ofthe plurality of RIP engines is compatible with each of RIP engines ofother available devices. Specifically, each of the plurality of RIPengines of the DFE 100 is compatible with each of the RIP engines ofother available devices that may transmit job data to the DFE 100 in theHWF system. Since the HWF servers 4 a and 4 b include different RIPengines, a plurality of the RIP engines that compatible with the RIPengines of HWF servers 4 a and 4 b is disposed in the DFE 100.

The job receiver 111 includes the plurality of specific job receivingunits 112. In this configuration, each of the specific job receivingunits 112 receives job data from the HWF server 4 via the network I/F101, and each of the plurality of specific job receiving units 112respectively corresponds to each of the plurality of RIP enginesdisposed in the DFE 100. In this configuration, the specific jobreceiving unit 112 can be used as a specific receiver.

As described above, when job data is transmitted from the HWF server 4to the DFE 100, the corresponding RIP engine 120 is designated, and thejob data is transmitted to the corresponding RIP engine 120. Therefore,the specific job receiving unit 112 in the job receiver 111,corresponding to the designated RIP engine 120, can receive the jobdata.

In the above described configuration, the job data can be input to theDFE 100 from the HWF server 4 via a network. Further, the job data canbe input to the DFE 100 via a portable memory such as a universal serialbus (USB) memory. In this description, the JDF information is includedin the job data. If the JDF information is not included in the job data,the job receiver 111 generates dummy JDF information, and assigns thedummy JDF information to the job data.

The specific job receiving units 112 can be disposed for each of theabove described RIP engines 120. Further, each of the specific jobreceiving unit 112 can be used as a virtual printer set with jobcontents in advance. Specifically, each of the specific job receivingunits 112 can be disposed for the corresponding RIP engine 120 disposedin the DFE 100 and job contents, and then, by designating any one of theplurality of specific job receiving units 112, the corresponding job canbe executed with the contents set in advance.

Further, as to the one or more example embodiment of the presentinvention, the specific job receiving unit 112 can be set with a“pass-through mode.” As illustrated in FIG. 6, the DFE 100 can includethe JDF analyzer 117, independently from the RIP engine 120, to performan analysis of JDF information. When the “pass-through mode” isactivated, the RIP engine 120 performs an analysis of the JDFinformation while the analysis of JDF information by the JDF analyzer117 is not activated.

By employing this configuration having the “pass-through mode,” JDFinformation using a format unprocessable by the JDF analyzer 117 can beused, a RIP engine that is difficult to include JDF analysis capabilityoutside the RIP engine can be employed for the HWF server 4 and the DFE100. As to the one or more example embodiments, the “pass-through mode”may be used when a plurality of processes is distributed between the RIPengine 420 disposed in the HWF server 4 and the RIP engine 120 disposedin the DFE 100, in which the RIP engine 120 and the RIP engine 420employs the same type of engine having the same capabilities. The RIPengine 120 can be used as an output-side image drawing informationgenerator or output-side drawing information generator, in which the RIPengine 120 generates the raster data as second image drawinginformation.

When the RIP processing is performed by the HWF server 4 and the DFE 100as the distributed processing, it is preferable that the RIP processingis performed as one sequential processing as much as possible withoutbeing perceived as separate processing by the HWF server 4 the DFE 100.Therefore, when data that is processed to the middle of the entireprocessing by the HWF server 4 is input to the DFE 100, it is preferablethat the processing is performed by the DFE 100 as a process beingcontinued from the HWF server 4 by omitting the JDF analysis processthat is performed normally when unprocessed job data is input to the DFE100.

As to the one or more example embodiments, the RIP engine having thesame capabilities is disposed in each of the HWF server 4 and the DFE100, with which the above described RIP processing can be controlled andperformed preferably. Further, in this configuration, it is preferablethat data processed by one RIP engine is transferred to another RIPengine as it is, which can be preferably implemented by using the“pass-through mode.”

The system controller 113 stores the job data received by the specificjob receiving unit 112 in the job data storage 114, or transfers the jobdata received by the specific job receiving unit 112 to the jobcontroller 116. If the DFE 100 is devised to store the job data, thesystem controller 113 stores the job data in the job data storage 114.Further, if the JDF information includes a description whether the jobdata is to be stored in the job data storage 114 or not, the systemcontroller 113 performs the processing in line with the description.

The job data is stored in the job data storage 114, for example, when apreview of print contents is performed by the DFE 100. In this case, thesystem controller 113 acquires data of a print target included in thejob data, which is PDL information and intermediate data, from the jobdata storage 114 to generate preview data, and transfers the previewdata to the UI controller 115. With this configuration, the UIcontroller 115 controls the display 102 to display a preview of theprint contents on the display 102.

When the preview data is to be generated, the system controller 113transfers the data of print target to the job controller 116, andrequests the job controller 116 to generate the preview data. The jobcontroller 116 transfers the data of print target to the RIP unit 118 togenerate the preview data, and the job controller 116 receives thegenerated preview data, and transfers the generated preview data to thesystem controller 113.

Further, when an operator changes the JDF information for the DFE 100,the job data is stored in the job data storage 114. In this case, thesystem controller 113 acquires the JDF information from the job datastorage 114, and transfers the JDF information to the UI controller 115.With this configuration, the JDF information of the job data isdisplayed on the display 102, and the operator can change the JDFinformation by performing an operation on the display 102.

When the operator changes the JDF information by operating the DFE 100,the UI controller 115 receives the changed information, and reports thechanged information to the system controller 113. The system controller113 applies the received changed information to the target JDFinformation to update the target JDF information, and stores the updatedtarget JDF information in the job data storage 114.

When the system controller 113 receives the job execution instruction,the system controller 113 reads out the job data stored in the job datastorage 114, and transfers the job data to the job controller 116. Thejob execution instruction can be input from the HWF server 4 via thenetwork or the job execution instruction can be input by an operation ofan operator to the DFE 100. Further, if the JDF information is set with,for example, the execution time, the system controller 113 transfers thejob data stored in the job data storage 114 to the job controller 116when the set execution time has come.

The job data storage 114 is a memory or a storage area to store the jobdata, which can be devised, for example, by the HDD 40 illustrated inFIG. 2. Further, the job data can be stored in a memory or a storagearea connected to the DFE 100 via a universal serial bus (USB)interface, or can be stored in a memory device connected or coupled viaa network.

As described above, the UI controller 115 controls the display 102 todisplay information, and receives an operation of an operator to the DFE100. When the above described editing process is performed to the JDFinformation, the UI controller 115 interprets the JDF information, anddisplays contents of the print job on the display 102.

The job controller 116 controls the job execution when the job executioninstruction is transmitted from the system controller 113. Specifically,the job controller 116 controls the JDF analysis process by the JDFanalyzer 117, the RIP processing by the RIP unit 118, and the control ofthe digital engine 150 by the printer controller 122.

When the job controller 116 receives the job execution instruction fromthe system controller 113, the job controller 116 inputs the JDFinformation included in the job data to the JDF analyzer 117 to requesta conversion of JDF. The JDF conversion request is a request ofconverting the JDF information described by a format used by an originalor initial generator of the JDF information to a format decodable orprocessable by the RIP unit 118. Therefore, the JDF analyzer 117 can beused as a process setting information converter.

By contrast, when the above described “pass-through mode” is designated,the job controller 116 acquires the JDF information included in the jobdata from the system controller 113, and inputs the acquired JDFinformation at it is to the RIP unit 118. The designation of“pass-through mode” can be described in the JDF information by using thespecific job receiving unit 112. Further, when the “pass-through mode”is designated by the specific job receiving unit 112, a “page mode” anda “sheet mode” can be also designated depending on the designated RIPengine 120.

The JDF analyzer 117 converts the JDF information described with theformat used by the original generator to the format decodable orprocessable by the RIP unit 118. The JDF analyzer 117 retains aconversion table therein, and extracts information required for the RIPunit 118 from information included in the JDF information, and convertsa description format of the extracted information based on theconversion table. With this configuration, the above described jobattribute in DFE can be generated.

FIG. 7 is an example of a conversion table retainable by the JDFanalyzer 117. As illustrated in FIG. 7, the conversion table correlatesa description format of JDF information and a description format of jobattribute in DFE. For example, information of “number of copies”illustrated in FIG. 3 is described as “A-Amount” in the original orinitial JDF information, and “A-Amount” is converted to a description of“number of copies” when generating the job attribute in DFE.

FIG. 7 is an example of a conversion table retainable by the JDFanalyzer 117. As illustrated in FIG. 7, the conversion table correlatesa description format of JDF information and a description format of jobattribute in DFE. For example, information of “number of copies”illustrated in FIG. 3 is described as “A-Amount” in the original orinitial JDF information, and “A-Amount” is converted to a description of“number of copies” when generating the job attribute in DFE.

The JDF analyzer 117 sets the “RIP control mode” to the job attribute inDFE when generating the job attribute in DFE. The “RIP control mode”includes the “page mode” and “sheet mode.” The JDF analyzer 117 assignsor allocates the “RIP control mode” based on a type of the specific jobreceiving unit 112 that has received the job data, job contents, and HWFsoftware program installed in the HWF server 4 used as a transmissionsource of the job data.

In the configuration described in this specification, condensed printingfor a print job can be set by using the “page mode.” The “RIP controlmode” will be described later in detail.

Based on the job attribute in DFE generated by the JDF analyzer 117, thejob controller 116 generates “RIP parameter,” and transfers the “RIPparameter” to the RIP controller 119 in the RIP unit 118 to execute theRIP processing. With this configuration, the RIP unit 118 can executethe RIP processing based on the “RIP parameter.”

FIG. 8 is an example of one set of RIP parameters of one or more exampleembodiments. The RIP parameters include, for example, “type ofinput/output data,” “data reading information,” and “RIP control mode”as header information. The “type of input/output data” designates thetype of input/output data such as JDF, PDL or the like. The designatableformat is, for example, JDF, PDL, text format, extension of image data,and intermediate data.

The “data reading information” includes information of a designationmethod and a designation position of reading position and writingposition of the input/output data. The “RIP control mode” is informationthat designates the “page mode” and “sheet mode.” The header informationfurther includes, for example, information of “unit” used in the RIPparameter, and information of compression method of data.

The “input/output image information” includes, for example, “informationof output image,” “information of input image,” and “information ofimage processing.” The “information of output image” includesinformation of, for example, format, resolution, size, color separation,color shift, and page orientation of output image data. The “informationof input image” includes information of, for example, format,resolution, page area, and color settings of input image data. The“information of image processing” includes information of, for example,an offset of enlargement/reduction algorism, an object area, and anoffset of halftone.

The “PDL information” is information related to PDL information used forthe RIP parameter. The “PDL information” includes information of, forexample, “data area,” “size information,” and “data arrangement method.”In this description, the PDL information is data of print target in ajob, and includes intermediate data. The “data area” designatesinformation of an area where the PDL information is stored. The “sizeinformation” designates a data size of the PDL information. The “dataarrangement method” designates a data arrangement pattern in a memorystoring the PDL information such as “little big endian” and “bigendian.”

When the “pass-through mode” is used, the job controller 116 generatesthe RIP parameter based on the JDF information and PDL information orthe JDF information and intermediate data. In this case, each of itemsconfiguring the RIP parameter is set with information useable forreferring corresponding items in JDF information.

As illustrated in FIG. 8, the RIP parameter includes the “RIP controlmode.” The RIP controller 119 controls the RIP engine 120 based on the“RIP control mode.” Therefore, the sequence is set based on the “RIPcontrol mode.” As above described, the “page mode” and “sheet mode” canbe set as the “RIP control mode.”

The “page mode” and “sheet mode” are performed to a plurality of pagesto generate raster data. As to the “page mode,” the RIP processing isperformed for each page of the plurality of pages, and then raster datacondensing the plurality of RIP-processed pages on one single sheet isgenerated. As to the “sheet mode,” a plurality of pages are condensed ona single sheet at first, and then the RIP processing is performed foreach part (i.e., each page) on the single sheet to generate raster datacondensing the plurality of pages on the single sheet.

Further, when the “pass-through mode” is set, the “pass-through mode”can be designated in the “RIP control mode.” However, this is just oneexample. The “pass-through mode” can be described in any items otherthan the “RIP control mode.”

Further, the job controller 116 sets “RIP engine identificationinformation” in the RIP parameter. The “RIP engine identificationinformation” is information for identifying each one of the plurality ofthe RIP engines 120 included in the RIP unit 118. In this configuration,the same RIP engine is used in the HWF server 4 as the RIP engine 420,and in the DFE 100 as the RIP engine 120.

Therefore, the JDF information includes information for designating thespecific job receiving unit 112 as described above, and the designatedspecific job receiving unit 112 receives the job data. Each one of thespecific job receiving units 112 corresponds to any one of the RIPengines 120, and identification information of the corresponding RIPengine 120 is added to the received JDF information. Based on theidentification information of the RIP engine 120 added to the JDFinformation, the job controller 116 adds the “RIP engine identificationinformation” to the RIP parameter.

As to the RIP unit 118, the RIP controller 119 controls the plurality ofRIP engines 120 to perform each of the internal processes of RIPprocessing based on the input RIP parameters to generate raster data. Asto the HWF system of the one or more example embodiments, since the RIPcontroller 119 may receive a plurality of print jobs from a plurality ofdifferent HWF servers 4, the RIP controller 119 is designed to processthe plurality of print jobs receivable from the plurality of differentHWF servers 4.

Each of the plurality of different HWF servers 4 may process data ofprint job differently. For example, the above described “page mode” and“sheet mode” of the “RIP control mode” may be differently set for eachof the different HWF servers 4. When one of the RIP engine 120 is setwith the “page mode,” and the condensed printing is to be performed bythe RIP engine 120, original page data corresponding to the condensingnumbers are designated sequentially.

By contrast, when another one of the RIP engines 120 is set with the“sheet mode,” and the condensed printing is to be performed by anotherRIP engine 120, all of original page data before performing thecondensing are designated, and then the RIP processing is performed forall of the original page data. Therefore, the methods of designatingparameters for the RIP engine 120 may become different for each of thedifferent RIP engines 120. This difference is not limited to the “RIPcontrol mode.” For example, differences may occur due to a difference offormat and processing of original data such as a difference ofprocessing of the margin of the original data.

To cope with the differences of the RIP engines 120, the RIP controller119 of the one or more example embodiments performs a conversion processof parameters designated to a specific RIP engine 120 depending on thespecific RIP engine 120 that is to perform a specific RIP processing.For example, when data of the “page mode” is input to the specific RIPengine 120 set with the “sheet mode,” parameters described by the “pagemode” are converted to parameters described by the “sheet mode.” Thecapabilities of the RIP engine 120 will be described later in detail.

The image storage 121 is a memory or a storage area to store raster datagenerated by the RIP engine 120. The image storage 121 can be devised,for example, by the HDD 40 illustrated in FIG. 2. Further, the imagestorage 121 can be a memory or a storage area connected to the DFE 100via a universal serial bus (USB) interface, or can be a memory deviceconnected or coupled via a network.

The printer controller 122 is connected or coupled to the digital engine150. The printer controller 122 reads the raster data stored in theimage storage 121, and transmits the raster data to the digital engine150 to execute a print output operation. Further, the printer controller122 acquires the finishing information included in the job attribute inDFE from the job controller 116 to control a finishing process.

The printer controller 122 can communicate information with the digitalengine 150 to acquire information of the digital engine 150. Forexample, when CIP4 standard is used, DevCaps standard is defined as theJDF information standard for communicating device property informationwith a printer. Further, printer information can be collected by using acommunication protocol such as simple network management protocol (SNMP)and a database such as management information base (MIB).

The device information manager 123 manages the device information suchas information of the DFE 100 and the digital engine 150. The deviceinformation includes, for example, information of the RIP engines 120included in the RIP unit 118, and information of the specific jobreceiving units 112 in the job receiver 111. Further, the information ofthe specific job receiving units 112 includes information of the abovedescribed “pass-through mode.”

The device information communication unit 124 communicates the deviceinformation with the HWF server 4 via the network I/F 101 using acompatible format such as MIB and job messaging format (JMF). With thisconfiguration, the device information communication unit 415 of the HWFserver 4 can acquire the device information from the DFE 100, with whichinformation of the RIP engines 120 and information of the specific jobreceiving units 112 included in the DFE 100 can be set to a GUI settableand displayable on the client terminal 5.

As to the DFE 100, when the printer controller 122 controls the digitalengine 150, and then a print output operation is completed, the systemcontroller 113 recognizes the completion of the print output operationvia the job controller 116. Then, the system controller 113 reports thecompletion of a job to the HWF server 4 via the job receiver 111. Withthis configuration, the job communication unit 421 of the HWF server 4receives a report of the completion of the job.

As to the HWF server 4, the job communication unit 421 transfers thereport of the completion of the job to the job controller 413, and thenthe job controller 413 reports the completion of the job to the workflowcontroller 418. The transmission of the job data from the HWF server 4to the DFE 10 is executed by the workflow controller 418 based on aworkflow information.

When the completion of the job by the DFE 100 is recognized, theworkflow controller 418 controls a next process based on the workflowinformation. A process to be performed after performing the print outputoperation by the DFE 100 is, for example, a post-processing by thepost-processing apparatus 3.

A description is given of a functional configuration of the RIP engineof the one or more example embodiments. FIG. 9 is a functionalconfiguration of the RIP engine 120 having the JDF analyzer 117 used forthe JDF analysis process. As above described, the RIP engine 120 can bea software module that executes each of the internal processes of RIPprocessing to generate raster data based on the RIP parameterillustrated in FIG. 8. The RIP engine 120 can be, for example, an Adobesystems PDF printing engine (APPE) provided by Adobe systems, but notlimited hereto.

As illustrated in FIG. 9, the RIP engine 120 is configured by a controlunit 201 and other units. The other units can be employed as extendedunits, which can be extended by a vendor. The control unit 201 executesthe RIP processing by using various capabilities that can be devised asthe extended units. Specifically, as illustrated in FIG. 9, the RIPengine 120 includes the control unit 201 and the extended units such asan input unit 202, a RIP parameter analyzer 203, a pre-fright processingunit 204, a normalize processing unit 205, a mark processing unit 206, afont processing unit 207, a color management module (CMM) processingunit 209, a trapping processing unit 210, a calibration processing unit211, a screening processing unit 212, an output unit 213 and a renderingprocessing unit 218.

The input unit 202 receives an initialization request, and an executionrequest of the RIP processing, and reports the request to the controlunit 201. When the initialization request is received, the abovedescribed RIP parameter is also input to the control unit 201. When thecontrol unit 201 receives the initialization request, the control unit201 inputs the RIP parameter, received at the same time with theinitialization request, to the RIP parameter analyzer 203. Then, thecontrol unit 201 acquires an analysis result of the RIP parameter,computed by the RIP parameter analyzer 203, and determines an activationsequence of each of the extended units included in the RIP engine 120when the RIP processing is performed. Further, the control unit 201determines a data format generatable by performing the RIP processing,in which the data format can be any one of the raster image, previewimage, PDF, and intermediate data.

Further, when the control unit 201 receives the execution request of theRIP processing from the input unit 202, the control unit 201 activateseach of the extended units included in the RIP engine 120 based on theactivation sequence that is determined when the control unit 201receives the initialization request. The pre-fright processing unit 204checks validity of input PDL data contents. If the pre-fright processingunit 204 detects an illegal PDL attribute, the pre-fright processingunit 204 reports the illegal PDL attribute to the control unit 201. Whenthe control unit 201 receives this report, the control unit 201 reportsthe illegal PDL attribute to an external module such as the RIPcontroller 119 and the job controller 116 via the output unit 213.

The pre-fright processing checks whether attribute information thatdisenables a processing by other modules included in the RIP engine 120is included in the received data. For example, the pre-fright processingchecks whether a font unable to be processed is designated or not.

The normalize processing unit 205 converts the input PDL data to PDF ifthe input PDL data is not PDF but PostScript. The mark processing unit206 applies graphic information of a designated mark, and superimposesthe graphic information at a designated position on an output targetprint image such as a target print image.

The font processing unit 207 extracts font data, and embeds the font toPDL data, and outlines the font. The color management module (CMM)processing unit 209 converts a color space of an input image to cyan,magenta, yellow, black (CMYK) based on a color conversion table set byInternational Color Consortium (ICC) profile. The ICC profile includescolor ICC information, and device ICC information.

The trapping processing unit 210 performs trapping processing. Whendifferent color regions are set adjacently via boundaries of thedifferent color regions, a gap may occur at the boundaries when apositional error occurs for the adjacently-set different color regions.The trapping processing expands each of the color regions to fill thegap.

The calibration processing unit 211 adjusts fluctuation of generatedcolor balance, caused by aging and individual difference of an outputdevice, to enhance precision of color conversion by the CMM processingunit 209. Further, the process by the calibration processing unit 211can be performed outside the RIP engine 120.

The screening processing unit 212 generates halftone dots in view of afinal output such as printed sheet. Further, the process by thescreening processing unit 212 can be performed outside the RIP engine120 similar to the calibration processing unit 211. The output unit 213transmits a RIP processing result to the outside of the RIP engine 120.The RIP processing result is any one of raster image, preview image,PDF, and intermediate data that are determined when the initializationis performed.

The rendering processing unit 218 performs a rendering processing togenerate the raster data based on the input data. Further, as to theconfiguration of FIG. 9, the processing of the mark processing unit 206,and the processing of the font processing unit 207 can be collectivelyexecuted by the rendering processing unit 218.

A description is given of another functional configuration of the RIPengine 120 with reference to FIG. 10. FIG. 10 is another functionalconfiguration of the RIP engine 120 without using the JDF analysisprocess by the JDF analyzer 117. As above described, a case that the JDFanalyzer 117 does not perform the JDF analysis process means that theinternal processes of RIP processing are performed by the HWF server 4and the DFE 100 as the distributed processing. Therefore, the HWF server4 includes the RIP engine 420 having the same configuration of the RIPengine 120 illustrated in FIG. 10.

As illustrated in FIG. 10, most of the functional configuration of theRIP engine 120 not using JDF analysis process by the JDF analyzer 117are same as the functional configuration of the RIP engine 120 of FIG.9. Hereinafter, portions different from the configuration of FIG. 9 aredescribed. Similar to FIG. 9, the units other than the control unit 201can be used as the extended units. Specifically, as illustrated in FIG.10, the RIP engine 120 includes the control unit 201 and the extendedunits such as the input unit 202, the pre-fright processing unit 204,the normalize processing unit 205, the mark processing unit 206, thefont processing unit 207, the color management module (CMM) processingunit 209, the trapping processing unit 210, the calibration processingunit 211, the screening processing unit 212, the output unit 213, a jobattribute analyzer 214, a RIP status analyzer 215, a RIP status manager216, a layout processing unit 217 and the rendering processing unit 218.

As to the configuration of FIG. 10, when the control unit 201 receivesan initialization request from the input unit 202, the control unit 201acquires the initialization request and the JDF information. Then, thecontrol unit 201 analyzes the JDF information and PDL information byusing the job attribute analyzer 214, and the control unit 201determines a process sequence of the extended units, and a data formatto be generated as a process result of each of the extended units sameas the configuration of FIG. 9.

As to the RIP engine 120 disposed in the DFE 100, data format obtainedas a process result by the RIP engine 120 often becomes the raster datato be input to the printer controller 122. By contrast, as to the RIPengine 420 disposed in the HWF server 4, data format obtained as aprocess result by the RIP engine 420 becomes different depending onpatterns of the distributed processing by the HWF server 4 and the DFE100. Therefore, the control unit 201 of the RIP engine 120 determinesthe data format (e.g., PDL information, intermediate data) of theprocess result based on an analysis result by the job attribute analyzer214.

Further, the control unit 201 analyzes the RIP status informationincluded in the JDF information by using the RIP status analyzer 215 tocheck whether one or more already-executed internal processes of RIPprocessing exist. If the already-executed internal process of the RIPprocessing unit exists, the corresponding extended unit is excluded fromthe target processing units of the RIP processing.

Further, the RIP status analyzer 215 can analyze the RIP status includedin the JDF information, and the RIP status analyzer 215 can similarlyanalyze the RIP status based on PDL information. In a case of analyzingthe PDL information, since the attribute information such as parameteris erased for the already-executed internal processes of RIP processing,it can determine which one or more of the internal processes of RIPprocessing are not yet performed based on the remaining attributeinformation.

The layout processing unit 217 performs the imposition process. Underthe control of the control unit 201, the RIP status manager 216 changesthe RIP status corresponding to each of the internal processes of RIPalready performed by each of the extended units to “Done”. The outputunit 213 transmits a RIP result to the outside of the RIP engine. TheRIP result is data having the data format that is determined when theinitialization is performed.

The rendering processing unit 218 of FIG. 10 performs the renderingprocessing to generate the raster data based on the input data same asthe configuration of FIG. 9. Further, as to the configuration of FIG.10, the processing of the mark processing unit 206, the processing ofthe font processing unit 207, and further the processing of the layoutprocessing unit 217 can be collectively executed by the renderingprocessing unit 218.

Further, as described above, the plurality of the RIP engines 120disposed in the DFE 100 such as “DFE (engine A)” and “DFE (engine B)”can be selectively used depending on information of the “RIP devicedesignation” included in the JDF information. Since the control unit 201cannot consign the processing to the extended units of other RIP engine,the job controller 116 can be used to consign the processing.

As described above, the job controller 116 adds the “RIP engineidentification information” to the RIP parameter. In this case, the jobcontroller 116 generates different RIP parameters for each of thedifferent internal processes of RIP processing designated with differentRIP engines 120. In an example case of FIG. 3, the RIP parameter of“engine A” is generated or designated for executing the “font” and“layout,” the RIP parameter of “engine B” is generated or designated forexecuting the “mark,” and the RIP parameter of “engine A” is generatedor designated for the subsequent processes after the “mark” asillustrated in FIG. 3.

Then, the job controller 116 requests the RIP unit 118 to perform theRIP processing based on each of the generated RIP parameters with aprocess sequence set for each of the internal processes of RIPprocessing. With this configuration, each of the internal processes ofRIP processing can be performed by selectively using the different RIPengines such as “engine A” and “engine B.”

In this process, each of the engines can perform only the designatedprocess by referring the “RIP status” information. Specifically, bysetting the status of to-be-processed items as “NotYet” and the statusof other items as “Done,” only the designated process can be performed.

Further, as to the above described HWF system according to one or moreexample embodiments, the RIP engine 420 disposed in the HWF server 4 andthe RIP engine 120 disposed in the DFE 100 employ the same RIP engine.In this description, the same RIP engine means that the RIP engine hasthe same configuration at least for generating the raster data.

Therefore, the RIP engine 420 and the RIP engine 120 may not employ thesame configuration for every one of the processing units illustrated inFIGS. 9 and 10. Specifically, the RIP engine 420 and the RIP engine 120employ the same configuration at least the one or more processing unitsillustrated in FIGS. 9 and 10 used for generating the raster data suchas the mark processing unit 206, the font processing unit 207, thelayout processing unit 217, and the rendering processing unit 218.Therefore, the RIP engine 420 and the RIP engine 120 employ the sameconfiguration for at least the processing units used for generating theraster data. Further, the RIP engine 420 and the RIP engine 120 canemploy the same configuration for other processing units as required.

A description is given of an operation of the HWF system of the one ormore example embodiments with reference to FIG. 11. FIG. 11 is asequential chart of an operation flow of the HWF system. FIG. 11 is anexample of a sequential chart when the digital printer 1 executes aprint output operation. As illustrated in FIG. 11, the deviceinformation communication unit 415 of the HWF server 4 acquires deviceinformation from the DFE 100 and the CTP 200 via a network, and thedevice information manager 416 registers the device information in thedevice information storage 417 (S1101). The process of S1101 can beperformed at regular intervals.

When a registration of job data is performed by an operation of anoperator to a GUI of the HWF system, the client terminal 5 transmits ajob registration request to the HWF server 4 (S1102), in which the UIcontroller 412 of the HWF server 4 acquires the job registrationrequest. With this configuration, the data receiver 411 acquires jobdata under the control of the system controller 410 (S1103).

When the data receiver 411 acquires the job data, the system controller410 controls the job controller 413 to convert a format of the acquiredjob data to PDL format (S1104), and the format-converted job data isregistered in the job data storage 414. As to the GUI that theregistration of job data is performed at S1102, an interface such as afile path for designating a registration target data, and an inputsection for designating each of information items in the JDF information(FIG. 3) can be displayed.

Further, by performing the process at step S1101, the HWF server 4 canacquire information of the type of the RIP engine disposed in the DFE100. Therefore, the information of the “RIP device designation” (FIG. 3)can be selectively input to the input section on the GUI of the clientterminal 5, in which when the DFE 100 is to perform the processing, aspecific RIP engine to perform the concerned processing can be selected.

Further, when a process of dividing the job data is performed inresponse to an operation of the operator to the GUI of the HWF system,the client terminal 5 transmits a job dividing request to the HWF server4 (S1105). When the job dividing request is issued at S51105, theoperator designates the job dividing pattern via an output destinationsetting screen illustrated in FIG. 12. FIG. 12 is an example ofinformation includable in the job dividing request transmitted at S1105.As illustrated in FIG. 12, information indicating a dividing target joband information indicating dividing contents are transmitted as the jobdividing request. In this example case, the information indicatingdividing contents is specifically correlated with a device to execute aprint output operation of each of the dividing contents. In an examplecase of FIG. 12, one device is correlated for executing a print outputoperation of some pages, and another device is correlated for executinga print output operation of other pages, in which the devices arecorrelated with the unit of “page.” The information indicated in FIG. 12can be used as output destination designation information thatdesignates different output destinations for different pages when theoutput target image includes a plurality of pages such as page data.

When the HWF server 4 receives the job dividing request, the systemcontroller 410 divides the dividing target job (i.e., job data)page-by-page based on the information indicating the dividing contents(FIG. 15) to generate a plurality of sub-job data configuring thedividing target job (S1106). In this process, the device designated foreach of the divided portions can be used as information of “devicedesignation” in the JDF information (FIG. 3). When the job data isdivided to generate the plurality of the sub-job data, each of thesub-job data is stored in the job data storage 414 as a discrete job.

Further, when a process of generating a workflow is performed inresponse to an operation of the operator to the GUI of the HWF system,the client terminal 5 transmits a workflow generation request to the HWFserver 4 (S1107). When the workflow generation request is transmitted,information designating the workflow contents and informationidentifying one or more jobs to be processed in line with the workflowinformation (FIG. 5) are transmitted.

When the HWF server 4 receives the workflow generation request, thesystem controller 410 inputs the information received with the workflowgeneration request to the workflow controller 418. With thisconfiguration, the workflow controller 418 generates a new workflowinformation based on the received information, and stores the newworkflow information in the workflow information storage 419, andcorrelates the new workflow information and the job identified by theworkflow generation request (S1108). The workflow and the job can becorrelated by adding, for example, an identifier identifying theworkflow to the JDF information.

When a job execution operation is performed on the client terminal 5such as when the job execution operation is performed in response to anoperation of an operator to the GUI on the client terminal 5 afterS1108, the client terminal 5 transmits a job execution request to theHWF server 4 (S1109). Further, steps S1102 to S1109 can be performed asdifferent processes, or steps S1102 to S1109 can be performed asone-time process that performs the job registration request, jobdividing request, workflow generation request, and job execution requestas one operation.

When the HWF server 4 receives the job execution request, the systemcontroller 410 acquires the designated job data from the job datastorage 414 based on information for identifying the job data receivedwith the job execution request (S110). Further, the system controller410 acquires the latest information of the device designated in theacquired job data from the device information manager 416, and sets theacquired latest device information to the job (51111).

Then, the system controller 410 transfers the job data to the workflowcontroller 418 to start an execution of the workflow (S1112). Theworkflow controller 418 acquires the workflow information correlated tothe acquired job data from the workflow information storage 419, andexecutes the processes in line with the workflow information.

As to the workflow processing, the processing in the HWF server 4 to beperformed by the RIP engine 420 disposed in the HWF server 4 is executedat first (S1113). At S1113, under the control of the workflow controller418, the job controller 413 controls the RIP engine 420 to execute theprocesses as described above.

When the workflow processing proceeds to a stage to transfer theworkflow processing to the DFE 100, under the control of the workflowcontroller 418, the job controller 413 controls the job communicationunit 421 to transmit the job data to the DFE 100 (S1114). At S1114, thejob controller 413 designates one of the specific job receiving units112 from the plurality of specific job receiving units 112 based oninformation designated in the JDF information.

When the job data is transmitted to the DFE 100, any one of theplurality of specific job receiving units 112 is designated, in whichthe specific job receiving unit 112 matched to the job data receives thejob data in the DFE 100. When the job data is input into the DFE 100, asdescribed above, the RIP processing and the output processing by thedigital engine 150 are performed in the DFE 100 (S1115).

When the DFE 100 completes the designated processes, the job receiver111 reports the completion notice of the processes to the HWF server 4(S1116). When the job controller 413 receives the completion notice ofthe processes from the DFE 100 via the job communication unit 421, thejob controller 413 reports the completion notice of the processes to theworkflow controller 418. Then, the workflow controller 418 transmits apost processing request to the post-processing apparatus 3 to execute apost-processing designated in the workflow executable after theprocessing at the DFE 100 (S1117).

At S1117, under the control of the workflow controller 418, the jobcontroller 413 controls the job communication unit 421 to transmit thepost processing request to the post-processing apparatus 3. Byperforming the above described processing, the operation of the HWFsystem completes.

A description is given of a detail of the internal processing in the DFE100 at S1115 (see FIG. 11) with reference to FIG. 13, which is a flowchart showing the steps of the processing in the DFE 100. As illustratedin FIG. 13, when the HWF server 4 transmit the job data to the DFE 100,the designated specific job receiving unit 112 receives the job data(S1301). After receiving the job data, the specific job receiving unit112 updates the JDF information to apply the discrete setting, set tothe specific job receiving unit 112, to the job data (S1302).

The above described “pass-through mode” can be also applied at S1302.The job data applied with the discrete setting is input to the systemcontroller 113, and then the system controller 113 stores the input jobdata in the job data storage 114 depending on the settings, and performsa preview processing via the UI controller 115 depending on an operationof an operator.

The job execution timing of the DFE 100 can be set as below. Forexample, the job is executed when the job execution of the DFE 100 isrequested by an operation of the operator, or when a timer counts theexecution time set in advance, the system controller 113 inputs the jobdata to the job controller 116. Then, the job controller 116 checkswhether the pass-through mode is set by referring the input job data(S1303). If the result is not the pass-through mode (S1303: NO), the jobcontroller 116 outputs the job data to the JDF analyzer 117 to generatethe job attribute in DFE (S1304).

If the result is the pass-through mode (S1303: YES) or the job attributein DFE is generated by performing the JDF conversion (S1304), the jobcontroller 116 generates the RIP parameter (S1305). If the result is notthe pass-through mode (S1303: NO), the RIP parameter illustrated in FIG.8 is generated at S1305. By contrast, if the result is the pass-throughmode (S1303: YES), the RIP parameter is generated for information otherthan “input/output image information” among the information illustratedin FIG. 8, and the JDF information is referred for the “input/outputimage information.”

When the job controller 116 generates the RIP parameter (S1305), the jobcontroller 116 inputs required information to the RIP unit 118 toexecute the RIP processing. In this sequence, when the RIP controller119 performs the above described parameter conversion (S1306), the RIPcontroller 119 designates the converted parameters to the RIP engine120, and instructs the RIP engine 120 to execute the RIP processing(S1307). With this configuration, the raster data can be generated bythe RIP engine 120.

At S1305, as described above, based on information of the “RIP devicedesignation” illustrated in FIG. 3, the RIP parameter can be generatedfor each one of the RIP engines. At S1307, the RIP processing isexecuted for each of the generated RIP parameters with a given processsequence to generate the raster data.

When the raster data is generated, and the job controller 116 acquiresthe raster data from the RIP unit 118, the job controller 116 inputs theraster data to the printer controller 122 to execute a print outputoperation by using the digital engine 150 (S1308). With this processingconfiguration, the internal processing in the DFE 100 is completed.

A description is given of a detail of the RIP processing at S1307 ofFIG. 13 with reference to FIG. 14. As illustrated in FIG. 14, based onthe initialization request input to the input unit 202, the control unit201 performs an initialization process (S1401). In an example case ofFIG. 9, at S1401, the RIP parameter analyzer 203 receives and analyzesthe RIP parameter, and determines one or more extended units to be usedfor executing one or more processes among the extended units included inthe RIP engine 120, and a process sequence of processing of the extendedunits as described above. Further, the RIP parameter analyzer 203determines a data format of data to be generated as a process resultwhen the processing is performed.

Further, in another example case of FIG. 10, the job attribute analyzer214 receives and analyzes JDF information and PDL information todetermine one or more extended units to be used for executing one ormore processes among the extended units included in the RIP engine 120,and a process sequence of processing of the extended units. Further, thejob attribute analyzer 214 determines a data format of data to begenerated as a process result when the processing is performed. Then, inanother example case of FIG. 10, the control unit 201 instructs the RIPstatus analyzer 215 to execute the status analysis.

As to the RIP status analysis, the RIP status analyzer 215 refers orchecks the “RIP status” (FIG. 3), and selects one item of the internalprocesses of RIP processing (S1402). If the status of the selected itemis “Done” (S1403: YES), the corresponding extended unit is excluded fromthe extended units determined as the execution targets at S1401 (S1404).If the status of the selected item is “NotYet” (S1403: NO), the sequenceproceeds to S1405.

The RIP status analyzer 215 repeats steps from S1402 to S1405 until allof the items of the internal processes of RIP processing is processed(S1405: NO). When the RIP status analyzer 215 completes steps from S1402to S1405 for all of the items of the internal processes of RIPprocessing (S1405: YES), and the input unit 202 acquires an executionrequest of the RIP processing (S1406: YES), the control unit 201controls each of the extended units to execute the RIP processing with agiven process sequence (S1407).

At S1407, the RIP processing is requested to one or more extended unitsdetermined at step S1401 and not excluded by the process at step S1404.Further, the RIP processing is requested to perform in line with theprocess sequence determined at step S1401. When the one or more extendedunits perform the RIP processing and the raster data is generated, theoutput unit 213 outputs a process result (S1408). With this processingconfiguration, the RIP processing by the RIP unit 118 completes.

In another example case of FIG. 10, steps S1402 to S1405 (i.e., statusanalysis) is performed only for the RIP engine 120 set with thepass-through mode because the status analysis is required when the RIPprocessing is divided and assigned for each of the HWF server 4 and theDFE 100 as described above.

Since the RIP engine disposed in the HWF server 4 and the RIP enginedisposed in the DFE 100 use the RIP engine having the substantially sameprocessing capabilities, the RIP processing can be performed as oneprocessing without recognizing a boundary of the HWF server 4 and theDFE 100. Therefore, it is preferable to input data processed by the RIPengine 420 of the HWF server 4 to the RIP engine 120 of the DFE 100 asthey are, in which the pass-through mode is suitable for the RIPprocessing because the JDF analyzer 117 disposed outside of the RIPengine 120 is not used.

However, this is just one example. Even if the pass-through mode is notused, the status analysis is required when the RIP processing is dividedand assigned to each of the HWF server 4 and the DFE 100. Specifically,when the RIP processing is divided and assigned to each of the HWFserver 4 and the DFE 100, the RIP processing already executed at the HWFserver 4 is required to be excluded from the RIP processing when the RIPprocessing is executed at the DFE 100.

Therefore, even if the RIP engine 120 is not set with the pass-throughmode, the RIP status analyzer 215 can be disposed to divide and assignthe RIP processing to each of the HWF server 4 and the DFE 100.Specifically, when the RIP processing is divided and assigned to each ofthe HWF server 4 and the DFE 100, the JDF analysis can be performed bythe JDF analyzer 117 at the DFE 100, and then the status analysis can beperformed by the RIP status analyzer 215 to determine which internalprocess of RIP processing is required to be processed.

As to the above described HWF system according to one or more exampleembodiments, the RIP engine 420 disposed in the HWF server 4 and the RIPengine 120 disposed in the DFE 100 can employ the substantially sameconfiguration as above described. Therefore, differences may not occurbetween the raster data of the print job processed by the RIP engine 420used for a print output operation of the offset printer 2, and theraster data of the print job processed by the RIP engine 120 used for aprint output operation of the digital printer 1. Therefore, differencesof printout results caused by using different image forming apparatusescan be reduced, in particular, can be prevented.

However, if settings of the resource data (hereinafter, RIP resourcedata) such as font data, which is image processing data or information,to be used for the RIP processing at the HWF server 4 and the digitalprinter 1 are different, the image data integrity in the raster data maybe lost. As to the example embodiment of the present invention, the RIPprocessing is performed by using the RIP resource data 422 d stored inthe HWF server 4. The RIP resource data includes, for example, colorconversion profile, font data, mark data, halftone screen data, and spotcolor matching data.

The color conversion profile is digitized color space information setfor each device. The color conversion profile includes information ofcoordinates of three primary colors, coordinates of white color, andtone response profile, which are used to secure the color tone of theoutput image. The font data is information to use the same font in theoutput image. The mark data is information to use the same mark (e.g.,crop color mark, color bar, text mark) in the output image.

The halftone screen data is information of ink arrangement density toset gradation in the output image. The spot color matching library isinformation to convert color ink other than C, M, Y, K color ink(hereinafter, specific color) to the same process color. For example,when image data using a specific color is input from the client terminal5, the RIP processing is performed by referring the spot color matchinglibrary stored in the HWF server 4 to convert the specific color toCMYK.

A description is given of the RIP processing performed in the DFE 100 byusing the RIP resource data 422 d stored in the HWF server 4 withreference to FIG. 15. FIG. 15 is a flow chart illustrating the steps ofa process of transmitting the RIP resource data 422 d stored in the HWFserver 4 to the DFE 100.

At first, the job controller 413 generates job data based on targetprint data acquired by the system controller 410 so that the DFE 100 canperform the RIP processing to the job data by referring the RIP resourcedata 422 d stored in the HWF server 4 (S1501). For example, based on anoperation by an operator at the client terminal 5, the job controller413 updates the job data so that the DFE 100 can perform the RIPprocessing by using the RIP resource data 422 d stored in the HWF server4.

Specifically, the above described image processing data or information(e.g., color conversion profile, font data, mark data, halftone screendata, spot color matching data) stored in the HWF server 4 can be usedby the DFE 100.

Then, it is determined whether the RIP resource data 422 d stored in theHWF server 4 is attached to the job data (S1502). If a data size of theRIP resource data 422 d, required for executing the RIP processing,stored in the HWF server 4 is greater than a given data size, the jobcontroller 413 updates the job data without attaching the RIP resourcedata 422 d (S1502: No), and prepares an instruction for referring theRIP resource data 422 d stored in the HWF server 4 (hereinafter,referring instruction of RIP resource data) (S1503). When the RIPresource data 422 d is not attached to the job data, the job controller413 updates the job data (S1505) by adding the referring instruction ofRIP resource data 422 d, stored in the HWF server 4, (S1503) asindicated in FIG. 16, which will be used when the DFE 100 performs theRIP processing.

If the data size of the RIP resource data 422 d, required for executingthe RIP processing, stored in the HWF server 4, is less than the givendata size (S1502: Yes), the job controller 413 attaches the RIP resourcedata 422 d, stored in the HWF server 4, to the job data (S1504) asindicated in FIG. 17, and updates the job data (S1505). The jobcommunication unit 421 transmits the job data updated by the jobcontroller 413 to the DFE 100 (S1506), and then the DFE 100 executes theRIP processing based on the updated job data.

As to the above described image processing system, the DFE 100 canexecute the RIP processing by using the RIP resource data 422 d storedin the HWF server 4. Therefore, even if the RIP resource data 422 dstored in the HWF server 4 is not stored in the DFE 100, the RIPprocessing executable in the HWF server 4 can be executed at the DFE100, and the raster data can be generated. In the above describedexample embodiment, the RIP resource data 422 d stored in the HWF server4 can be used as control-side image processing data or information,which may be referred to as first image processing data, while the RIPresource data 125 d stored in the DFE 100 can be used as output-sideimage processing data or information, which may be referred to as secondimage processing data. Therefore, even if settings of the RIP resourcedata, which is used as the image processing data or information for theRIP processing at the HWF server 4 and the digital printer 1 aredifferent, the image data integrity in the raster data can bemaintained.

Further, the job controller 413 can determine whether the RIP resourcedata 422 d stored in the HWF server 4 is attached to the job data basedon a communication busy status of communication line of the imageprocessing system. Further, if a data size of the job data is greaterthan the given data size, the job controller 413 can update the job databy adding a description of referring the RIP resource data 422 d storedin the HWF server 4.

(Second Example Embodiment)

As to the above described image processing system of the first exampleembodiment, it is assumed that the RIP engine disposed in the HWF server4 and the RIP engine disposed the DFE 100 have the same processingcapabilities. However, when the software is updated, the version of theRIP engine 420 and the version of the RIP engine 120 may becomedifferent, with which the output result of the RIP processing by the RIPengine 420 and the output result of the RIP processing by the RIP engine120 may become different. Therefore, in the second example embodiment,the version of the RIP engine 420 and the version of the RIP engine 120are compared, and then a device or apparatus to execute the RIPprocessing is determined based on the comparison result.

FIG. 18 is an example of modification of software when the RIP engine isdeveloped in the software development process. The RIP engine generatesthe raster data to be used for a printing operation based on image datainput to the HWF server 4. Therefore, as indicated in FIG. 18, when thesoftware is updated to improve the image expression when the printingoperation is performed, the version of the RIP engine may be changed.

As indicated in the updating process of software (FIG. 18), the colorexpression setting a priority on rich black is set for VerX.0. Then,transparency effect and overprint are changed and the color expressionsetting a priority on alternative color is set for VerX.1. When the RIPengine of one version and the RIP engine of another version perform theRIP processing based on the same image data, the output result of theRIP processing by the RIP engine 420 and the output result of the RIPprocessing by the RIP engine 120 may become different. For example, thearrangement and color of the drawn objects may become different.

Therefore, when the modification of software (see FIG. 18) is applied tothe HWF server 4 and the DFE 100 independently, even if the RIP enginedisposed in the HWF server 4 and the RIP engine disposed the DFE 100have the same processing capabilities, the output result of the RIPprocessing by the RIP engine 420 and the output result of the RIPprocessing by the RIP engine 120 may become different because theversion of the RIP engine 420 and the version of the RIP engine 120 aredifferent.

Therefore, based on the version information including image processingdata or information that is processed at the RIP engine 420 having oneversion and the RIP engine 120 having another version, the systemcontroller 410 determines whether the output result of the RIPprocessing by the RIP engine 420 and the output result of the RIPprocessing by the RIP engine 120 become different. Therefore, theversion information of the RIP engine 420 is used as the control-sideimage processing data or information, which may be referred to as firstimage processing data, and while the version information of the RIPengine 120 is used as the output-side image processing data orinformation, which may be referred to as second image processing data.

When the system controller 410 determines whether the output result ofthe RIP processing by the RIP engine 420 and the output result of theRIP processing by the RIP engine 120 become different, the systemcontroller 410 perform the determination based on image processing dataor information to be referred when the raster data is generated.Specifically, the system controller 410 determines whether the outputresult of the RIP processing by the RIP engine 420 and the output resultof the RIP processing by the RIP engine 120 become different based onthe description of the parameters of the internal processing of the RIPprocessing set for the RIP engine 420 having one version and the RIPengine 120 having another version.

Further, if the system that manages the development of the RIP engine isused, the system controller 410 can determine whether the output resultof the RIP processing by the RIP engine 420 and the output result of theRIP processing by the RIP engine 120 become different by referringcapability information that is changed when the version is changed.

Further, when the output result of the RIP processing by the RIP engine420 and the output result of the RIP processing by the RIP engine 120become different due to the version information of the RIP engine 420and the version information of the RIP engine 120, the output differencecan be stored in the device information storage 417 as a list asindicated in FIG. 19. FIG. 19 is an example of a table associatingcapabilities installed for the RIP engine 420 having one version and theRIP engine 120 having another version, and the differences of the outputresult of the RIP processing by the RIP engine 420 having one versionand the RIP engine 120 having another version.

Further, the system controller 410 can determine whether the outputresult of the RIP processing by the RIP engine 420 and the output resultof the RIP processing by the RIP engine 120 become different byreferring the output difference list (see FIG. 19) by using the deviceinformation manager 416 via the network. Then, based on thedetermination result, a device or apparatus to perform the RIPprocessing is determined in the second example embodiment.

A description is given of a process of determining a device or apparatusto perform the RIP processing with reference to FIG. 20. FIG. 20 is aflow chart illustrating the steps of a process of determining a deviceor apparatus to perform the RIP processing by using the HWF server 4based on a difference of the output result of the RIP processing by theRIP engine 420 having one version and the output result of the RIPprocessing by the RIP engine 120 having another version.

Based on image data input from the client terminal 5, the systemcontroller 410 instructs the job controller 413 to generate job data.Then, the job controller 413 transmits the generated job data to the RIPengine 420. When the RIP engine 420 receives the job data (S2001), theRIP engine 420 analyzes JDF information included in the job data toperform a pre-fright processing (S2002). At S2002, it is determinedwhich process included in the RIP processing is performed at the RIPengine 420 when the RIP engine 420 performs the RIP processing based onthe received job data.

After the job controller 413 generates the job data, the systemcontroller 410 acquires the version information of the RIP engine 420and the version information of the RIP engine 120 via the deviceinformation manager 416.

Then, based on the acquired version information and the pre-frightprocessing result performed by the RIP engine 420, the system controller410 determines whether the output difference occurs between the RIPprocessing by the RIP engine 420 and the RIP processing by the RIPengine 120 when the RIP processing is performed at the RIP engine 420and the RIP engine 120 (S2003). Therefore, the job controller 413 can beused as a control-side difference determination unit.

When the pre-fright processing of the job data is performed (S2002), thesystem controller 410 can determine that the sequential order andpriority of processes to be performed for the RIP processing by usingthe RIP engine 420 having one version and the RIP engine 120 havinganother version become difference, and then the system controller 410determines that the output difference occurs.

Further, the system controller 410 can determine that the outputdifference occurs when the capabilities listed in the output differencelist (see FIG. 19) are performed by the RIP processing. Then the jobcontroller 413 updates the job data based on the determination result ofthe system controller 410 at S2003.

If the system controller 410 determines that the output difference doesnot occur to the output result of the RIP processing by the RIP engine420 and the output result of the RIP processing by the RIP engine 120(S2003: NO), the job controller 413 transmits the job data, which is tobe RIP processed at the RIP engine 120, to the DFE 100 (S2004). When theDFE 100 receives the job data, the RIP engine 120 performs the RIPprocessing required for generating the raster data.

If the system controller 410 determines that the output differenceoccurs to the output result of the RIP processing by the RIP engine 420and the output result of the RIP processing by the RIP engine 120(S2003: YES), the job controller 413 updates the job data so that theRIP processing required for generating the raster data is performed atthe HWF server 4 (S2005).

At this stage, the job data can be updated by controlling the RIP statusbased on the pre-fright processing result at S2002.

For example, the RIP status is controlled so that the RIP engine 420disposed in the HWF server 4 performs the RIP processing for one or morecapabilities that the output difference will occur alone.

Then, the job controller 413 instructs the RIP engine 420 to perform theRIP processing based on the updated job data. When the RIP engine 420performs the RIP processing, the RIP engine 420 generates data processedby the RIP processing, and this data is referred to as the RIP-processeddata. The system controller 410 transmits the job data including theRIP-processed data to the DFE 100 (S2006). Then, the DFE 100 performsthe printing operation based on the job data including the RIP-processeddata received from the system controller 410.

At this stage, if the RIP engine 420 performs the RIP processing to oneor more capabilities that the output difference will occur alone, theDFE 100 can sequentially perform the RIP processing for othercapabilities to the job data received from the system controller 410.

As above described, based on the output difference of the RIP engine 420and the RIP engine 120, the HWF server 4 determines the device orapparatus to perform the RIP processing.

Further, the device or apparatus to perform the RIP processing can bedetermined by the DFE 100. Specifically, when the DFE 100 receives thejob data, the RIP engine 120 can perform the pre-fright processing tothe received job data. Based on the pre-fright processing result by theRIP engine 120, the device or apparatus to perform the RIP processingcan be determined. A description is given of a process of determiningthe device or apparatus to perform the RIP processing by using the DFE100 with reference to FIG. 21.

FIG. 21 is a flow chart illustrating the steps of a process ofdetermining the device or apparatus to perform the RIP processing byusing the DFE 100 when the output difference occurs due to the RIPengine 420 having one version and the RIP engine 120 having anotherversion.

When the RIP engine 120 receives the job data (S2101), the RIP engine120 analyzes JDF information included in the job data to perform apre-fright processing (S2102). At S2102, it is determined which processincluded in the RIP processing is to be performed at the RIP engine 120when the RIP engine 120 performs the RIP processing based on thereceived job data.

After the job controller 116 generates the job data, the systemcontroller 113 acquires the device information based on the versioninformation of the RIP engine 420 and the version information of the RIPengine 120 via the device information manager 123.

Then, based on the acquired version information and the pre-frightprocessing result performed by the RIP engine 120,

the system controller 113 determines whether the output differenceoccurs between the RIP processing by the RIP engine 420 and the RIPprocessing by the RIP engine 120 when the RIP processing is performed atthe RIP engine 420 and the RIP engine 120 (S2103). Therefore, the jobcontroller 116 can be used as an output-side difference determinationunit.

The job controller 116 updates the job data based on the determinationresult of the system controller 113 at S2103. Further, the systemcontroller 113 determines whether the output difference occurs due tothe difference of the RIP engine 420 and the RIP engine 120 similar tothe system controller 410.

If the system controller 113 determines that the output difference doesnot occur to the output result of the RIP processing by the RIP engine420 and the output result of the RIP processing by the RIP engine 120(S2103: NO), the job controller 116 instructs the RIP engine 120 toperform the RIP processing (S2104) in the DFE 100.

If the system controller 113 determines that the output difference occurto the output result of the RIP processing by the RIP engine 420 and theoutput result of the RIP processing by the RIP engine 120 (S2103: YES),the job controller 116 updates the job data so that the RIP processingrequired for generating the raster data is performed at the HWF server 4(S2105).

At this stage, the job data can be updated by controlling the RIP statusbased on the pre-fright processing result at S2102. For example, the RIPstatus is controlled so that the RIP engine 420 disposed in the HWFserver 4 performs the RIP processing for one or more capabilities thatthe output difference will occur alone, in which the updated job data istransmitted from the system controller 113 to the HWF server 4 via thejob receiver 111 (S2106).

Then, the job controller 413 instructs the RIP engine 420 to perform theRIP processing based on the job data received from the DFE 100, in whichit can be configured that the RIP engine 420 performs the RIP processingto the one or more capabilities that the output difference will occuralone,

When the RIP engine 420 performs the RIP processing, the RIP engine 420generates data processed by the RIP processing, and this data isreferred to as the RIP-processed data. The system controller 410transmits the job data including the RIP-processed data to the DFE 100via the data receiver 411. Then, the DFE 100 receives the job dataincluding the RIP-processed data (S2107), and performs the printingoperation. As above described, the DFE 100 can determine the device orapparatus to perform the RIP processing based on the output differenceof the RIP engine 420 and the RIP engine 120.

As to the above described image processing system, when the differenceis to occur to the printed products due to the difference of the RIPprocessing by the RIP engine disposed in the HWF server 4 and the RIPprocessing by the RIP engine disposed in the DFE 100, the HWF server 4performs the RIP processing. With employing this configuration, thedifferences of the printed products between the digital printer 1 andthe offset printer 2 can be reduced, in particular prevented.

As to the above described image processing system, the HWF server 4performs the RIP processing to reduce the differences of the printedproducts between the digital printer 1 and the offset printer 2 becausethe HWF server 4 generates the raster data to be used for the plate ofthe offset printer 2.

Each of the functions of the described embodiments may be implemented byone or more processing circuits or circuitry. Processing circuitryincludes a programmed processor, as a processor includes circuitry. Aprocessing circuit also includes devices such as an application specificintegrated circuit (ASIC), digital signal processor (DSP), fieldprogrammable gate array (FPGA), and conventional circuit componentsarranged to perform the recited functions. Further, the above describedimage processing method performable in the image processing apparatuscan be described as a computer-executable program, and thecomputer-executable program can be stored in a ROM or the like in theimage processing apparatus and executed by the image processingapparatus. Further, the computer-executable program can be stored in astorage medium or a carrier such as compact disc-read only memory(CD-ROM), digital versatile disc-read only memory (DVD-ROM) or the likefor distribution, or can be stored on a storage on a network anddownloaded as required.

Numerous additional modifications and variations for the communicationterminal, information processing system, and information processingmethod, a program to execute the information processing method by acomputer, and a storage or carrier medium of the program are possible inlight of the above teachings. It is therefore to be understood thatwithin the scope of the appended claims, the disclosure of the presentinvention may be practiced otherwise than as specifically describedherein. For example, elements and/or features of different examples andillustrative embodiments may be combined each other and/or substitutedfor each other within the scope of this disclosure and appended claims.

What is claimed is:
 1. An image processing system, comprising: an offsetprinter; a digital printer; and a server that is communicable with theoffset printer and the digital printer, the server including processingcircuitry configured to: perform a first image processing to generatefirst raster data based on print target data, the first raster data tobe used for generating a plate that is used by the offset printer; andperform a second image processing to generate second raster data basedon the print target data, the second raster data used by the digitalprinter, wherein a first image formed by the offset printer and a secondimage formed by the digital printer are substantially the same, theoffset printer uses the plate to form the first image on a recordingmedium, the digital printer uses the second raster data to form thesecond image on the recording medium, the digital printer includessecond processing circuity, and the processing circuitry performs a partof the second image processing and the second processing circuitryperforms another part of the second image processing.
 2. The imageprocessing system of claim 1, wherein the processing circuitry and thesecond processing circuitry perform a same function.
 3. The imageprocessing system of claim 1, wherein the processing circuitry isfurther configured to detect whether the processing circuitry and thesecond processing circuitry perform a same function, and when theprocessing circuitry and the second processing circuitry are detected tonot perform the same function, the processing circuitry updates theprint target data.
 4. A digital printer communicable with a server,comprising: processing circuitry configured to receive intermediate datafrom the server, the server performing first image processing togenerate first raster data based on print target data, and performing apart of second image processing to generate the intermediate data, basedon the print target data, perform another part of the second imageprocessing on the intermediate data to generate second raster data, anduse the second raster data to form a second image on a recording medium,wherein a first image formed by an offset printer and the second imageformed by the processing circuitry are substantially the same, the firstraster data is used to generate a plate used by the offset printer, andthe offset printer uses the plate to form the first image on therecording medium.
 5. An image processing system, comprising: a digitalprinter; and a server that is communicable with the digital printer andanother image forming apparatus, the server including processingcircuitry configured to: perform a first image processing to generatefirst raster data based on print target data, the first raster beingused by the another image forming apparatus, and perform a second imageprocessing to generate second raster data based on the print targetdata, the second raster data being used by the digital printer, whereina first image formed by the another image forming apparatus on arecording medium and a second image formed by the digital printer on therecording medium are substantially the same; the digital printerincludes second processing circuitry; and the processing circuitryperforms a part of the second image processing and the second processingcircuitry performs another part of the second image processing.
 6. Theimage processing system of claim 5, wherein the image processing systemfurther comprises the another image forming apparatus, which uses thefirst raster data to form the first image on the recording medium, andthe digital printer uses the second raster data to form the second imageon the recording medium.
 7. The image processing system of claim 5,wherein the processing circuitry and the second processing circuitryperform a same function.
 8. The image processing system of claim 5,wherein the processing circuitry is further configured to detect whetherthe processing circuitry and the second processing circuitry perform asame function, and when the processing circuitry and the secondprocessing circuitry are detected to not perform the same function, theprocessing circuitry updates the print target data.